Deactivation of PUCCH Secondary Cell in PUCCH Group

ABSTRACT

A base station transmits, to a wireless device, a configuration of a physical uplink control channel (PUCCH) group including a first secondary cell with a secondary PUCCH, and a second secondary cell. The base station transmits, in a first subframe, a media access control command including a bitmap indicating deactivation of the first secondary cell. In response to the deactivation of the first secondary cell, reception of channel state information for the second secondary cell is stopped in a second subframe that is eight subframes after the first subframe and stopping the reception does not occur before the second subframe.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/600,969, filed Oct. 14, 2019, which is a continuation of U.S.application Ser. No. 15/070,038, filed Mar. 15, 2016, which claims thebenefit of U.S. Provisional Application No. 62/133,947, filed Mar. 16,2015, the contents of each of which are hereby incorporated by referencein their entireties.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present invention.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present invention.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention.

FIG. 6 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present invention.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention.

FIG. 10 is an example grouping of cells into PUCCH groups as per anaspect of an embodiment of the present invention.

FIG. 11 illustrates example groupings of cells into one or more PUCCHgroups and one or more TAGs as per an aspect of an embodiment of thepresent invention.

FIG. 12 illustrates example groupings of cells into one or more PUCCHgroups and one or more TAGs as per an aspect of an embodiment of thepresent invention.

FIG. 13 is an example MAC PDU as per an aspect of an embodiment of thepresent invention.

FIGS. 14A and 14B are example CQI tables as per an aspect of anembodiment of the present invention.

FIGS. 15A and 15B are example diagrams illustrating timing of someevents according to the current LTE-Advanced transceivers.

FIGS. 16A and 16B are example diagrams illustrating timing of someevents as per an aspect of an embodiment of the present invention.

FIG. 17 is an example diagram illustrating timing of some events as peran aspect of an embodiment of the present invention.

FIG. 18 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 21 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 22 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 23 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 24 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 25 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 26 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

FIG. 31 is an example flow diagram as per an aspect of an embodiment ofthe present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation ofmultiple physical uplink control channel (PUCCH) groups. Embodiments ofthe technology disclosed herein may be employed in the technical fieldof multicarrier communication systems. More particularly, theembodiments of the technology disclosed herein may relate to operationof PUCCH groups.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CSI channel state information

CDMA code division multiple access

CSS common search space

CPLD complex programmable logic devices

CC component carrier

DL downlink

DCI downlink control information

DC dual connectivity

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FPGA field programmable gate arrays

FDD frequency division multiplexing

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MCG master cell group

MeNB master evolved node B

MIB master information block

MAC media access control

MAC media access control

MME mobility management entity

NAS non-access stratum

OFDM orthogonal frequency division multiplexing

PDCP packet data convergence protocol

PDU packet data unit

PHY physical

PDCCH physical downlink control channel

PHICH physical HARQ indicator channel

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

PCell primary cell

PCell primary cell

PCC primary component carrier

PSCell primary secondary cell

pTAG primary timing advance group

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RBG Resource Block Groups

RLC radio link control

RRC radio resource control

RA random access

RB resource blocks

SCC secondary component carrier

SCell secondary cell

Scell secondary cells

SCG secondary cell group

SeNB secondary evolved node B

sTAGs secondary timing advance group

SDU service data unit

S-GW serving gateway

SRB signaling radio bearer

SC-OFDM single carrier-OFDM

SFN system frame number

SIB system information block

TAI tracking area identifier

TAT time alignment timer

TDD time division duplexing

TDMA time division multiple access

TA timing advance

TAG timing advance group

TB transport block

UL uplink

UE user equipment

VHDL VHSIC hardware description language

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present invention. As illustrated in thisexample, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, SC-OFDM technology, or the like. For example, arrow 101shows a subcarrier transmitting information symbols. FIG. 1 is forillustration purposes, and a typical multicarrier OFDM system mayinclude more subcarriers in a carrier. For example, the number ofsubcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentinvention. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) mayconsist of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 203.The number of OFDM symbols 203 in a slot 206 may depend on the cyclicprefix length and subcarrier spacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present invention. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs (in this example 6 to 100 RBs) may depend,at least in part, on the downlink transmission bandwidth 306 configuredin the cell. The smallest radio resource unit may be called a resourceelement (e.g. 301). Resource elements may be grouped into resourceblocks (e.g. 302). Resource blocks may be grouped into larger radioresources called Resource Block Groups (RBG) (e.g. 303). The transmittedsignal in slot 206 may be described by one or several resource grids ofa plurality of subcarriers and a plurality of OFDM symbols. Resourceblocks may be used to describe the mapping of certain physical channelsto resource elements. Other pre-defined groupings of physical resourceelements may be implemented in the system depending on the radiotechnology. For example, 24 subcarriers may be grouped as a radio blockfor a duration of 5 msec. In an illustrative example, a resource blockmay correspond to one slot in the time domain and 180 kHz in thefrequency domain (for 15 KHz subcarrier bandwidth and 12 subcarriers).

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present invention. FIG. 5A shows an example uplink physical channel.The baseband signal representing the physical uplink shared channel mayperform the following processes. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments. The functions may comprise scrambling,modulation of scrambled bits to generate complex-valued symbols, mappingof the complex-valued modulation symbols onto one or severaltransmission layers, transform precoding to generate complex-valuedsymbols, precoding of the complex-valued symbols, mapping of precodedcomplex-valued symbols to resource elements, generation ofcomplex-valued time-domain SC-FDMA signal for each antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued SC-FDMA baseband signal for each antenna port and/or thecomplex-valued PRACH baseband signal is shown in FIG. 5B. Filtering maybe employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in each ofthe codewords to be transmitted on a physical channel; modulation ofscrambled bits to generate complex-valued modulation symbols; mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on each layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for each antenna port to resource elements;generation of complex-valued time-domain OFDM signal for each antennaport, and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for each antenna port is shown inFIG. 5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present invention.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, an LTE networkmay include a multitude of base stations, providing a user planePDCP/RLC/MAC/PHY and control plane (RRC) protocol terminations towardsthe wireless device. The base station(s) may be interconnected withother base station(s) (e.g. employing an X2 interface). The basestations may also be connected employing, for example, an S1 interfaceto an EPC. For example, the base stations may be interconnected to theMME employing the S1-MME interface and to the S-G) employing the S1-Uinterface. The S1 interface may support a many-to-many relation betweenMMEs/Serving Gateways and base stations. A base station may include manysectors for example: 1, 2, 3, 4, or 6 sectors. A base station mayinclude many cells, for example, ranging from 1 to 50 cells or more. Acell may be categorized, for example, as a primary cell or secondarycell. At RRC connection establishment/re-establishment/handover, oneserving cell may provide the NAS (non-access stratum) mobilityinformation (e.g. TAI), and at RRC connection re-establishment/handover,one serving cell may provide the security input. This cell may bereferred to as the Primary Cell (PCell). In the downlink, the carriercorresponding to the PCell may be the Downlink Primary Component Carrier(DL PCC), while in the uplink, it may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC), while in theuplink, it may be an Uplink Secondary Component Carrier (UL SCC). AnSCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE release with agiven capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTEtechnology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand DC as per an aspect of an embodiment of the present invention.E-UTRAN may support Dual Connectivity (DC) operation whereby a multipleRX/TX UE in RRC CONNECTED may be configured to utilize radio resourcesprovided by two schedulers located in two eNBs connected via a non-idealbackhaul over the X2 interface. eNBs involved in DC for a certain UE mayassume two different roles: an eNB may either act as an MeNB or as anSeNB. In DC a UE may be connected to one MeNB and one SeNB. Mechanismsimplemented in DC may be extended to cover more than two eNBs. FIG. 7illustrates one example structure for the UE side MAC entities when aMaster Cell Group (MCG) and a Secondary Cell Group (SCG) are configured,and it may not restrict implementation. Media Broadcast MulticastService (MBMS) reception is not shown in this figure for simplicity.

In DC, the radio protocol architecture that a particular bearer uses maydepend on how the bearer is setup. Three alternatives may exist, an MCGbearer, an SCG bearer and a split bearer as shown in FIG. 6. RRC may belocated in MeNB and SRBs may be configured as a MCG bearer type and mayuse the radio resources of the MeNB. DC may also be described as havingat least one bearer configured to use radio resources provided by theSeNB. DC may or may not be configured/implemented in example embodimentsof the invention.

In the case of DC, the UE may be configured with two MAC entities: oneMAC entity for MeNB, and one MAC entity for SeNB. In DC, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the MeNB, and theSecondary Cell Group (SCG) containing the serving cells of the SeNB. Fora SCG, one or more of the following may be applied: at least one cell inthe SCG has a configured UL CC and one of them, named PSCell (or PCellof SCG, or sometimes called PCell), is configured with PUCCH resources;when the SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or the maximum number of RLC retransmissionshas been reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: a RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG are stopped, a MeNB may beinformed by the UE of a SCG failure type, for split bearer, the DL datatransfer over the MeNB is maintained; the RLC AM bearer may beconfigured for the split bearer; like PCell, PSCell may not bede-activated; PSCell may be changed with a SCG change (e.g. withsecurity key change and a RACH procedure); and/or neither a directbearer type change between a Split bearer and a SCG bearer norsimultaneous configuration of a SCG and a Split bearer are supported.

With respect to the interaction between a MeNB and a SeNB, one or moreof the following principles may be applied: the MeNB may maintain theRRM measurement configuration of the UE and may, (e.g., based onreceived measurement reports or traffic conditions or bearer types),decide to ask a SeNB to provide additional resources (serving cells) fora UE; upon receiving a request from the MeNB, a SeNB may create acontainer that may result in the configuration of additional servingcells for the UE (or decide that it has no resource available to do so);for UE capability coordination, the MeNB may provide (part of) the ASconfiguration and the UE capabilities to the SeNB; the MeNB and the SeNBmay exchange information about a UE configuration by employing of RRCcontainers (inter-node messages) carried in X2 messages; the SeNB mayinitiate a reconfiguration of its existing serving cells (e.g., PUCCHtowards the SeNB); the SeNB may decide which cell is the PSCell withinthe SCG; the MeNB may not change the content of the RRC configurationprovided by the SeNB; in the case of a SCG addition and a SCG SCelladdition, the MeNB may provide the latest measurement results for theSCG cell(s); both a MeNB and a SeNB may know the SFN and subframe offsetof each other by OAM, (e.g., for the purpose of DRX alignment andidentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of the cell as for CA, except for the SFN acquiredfrom a MIB of the PSCell of a SCG.

According to some of the various aspects of embodiments, serving cellshaving an uplink to which the same time alignment (TA) applies may begrouped in a TA group (TAG). Serving cells in one TAG may use the sametiming reference. For a given TAG, user equipment (UE) may use onedownlink carrier as a timing reference at a given time. The UE may use adownlink carrier in a TAG as a timing reference for that TAG. For agiven TAG, a UE may synchronize uplink subframe and frame transmissiontiming of uplink carriers belonging to the same TAG. According to someof the various aspects of embodiments, serving cells having an uplink towhich the same TA applies may correspond to serving cells hosted by thesame receiver. A TA group may comprise at least one serving cell with aconfigured uplink. A UE supporting multiple TAs may support two or moreTA groups. One TA group may contain the PCell and may be called aprimary TAG (pTAG). In a multiple TAG configuration, at least one TAgroup may not contain the PCell and may be called a secondary TAG(sTAG). Carriers within the same TA group may use the same TA value andthe same timing reference. When DC is configured, cells belonging to acell group (MCG or SCG) may be grouped into multiple TAGs including apTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present invention. In Example 1, pTAG comprises PCell,and an sTAG comprises SCell1. In Example 2, a pTAG comprises a PCell andSCell1, and an sTAG comprises SCell2 and SCell3. In Example 3, pTAGcomprises PCell and SCell1, and an sTAG1 includes SCell2 and SCell3, andsTAG2 comprises SCell4. Up to four TAGs may be supported in a cell group(MCG or SCG) and other example TAG configurations may also be provided.In various examples in this disclosure, example mechanisms are describedfor a pTAG and an sTAG. The operation with one example sTAG isdescribed, and the same operation may be applicable to other sTAGs. Theexample mechanisms may be applied to configurations with multiple sTAGs.

According to some of the various aspects of embodiments, TA maintenance,pathloss reference handling and a timing reference for a pTAG may followLTE release 10 principles in the MCG and/or SCG. The UE may need tomeasure downlink pathloss to calculate uplink transmit power. A pathlossreference may be used for uplink power control and/or transmission ofrandom access preamble(s). UE may measure downlink pathloss usingsignals received on a pathloss reference cell. For SCell(s) in a pTAG,the choice of a pathloss reference for cells may be selected from and/orbe limited to the following two options: a) the downlink SCell linked toan uplink SCell using system information block 2 (SIB2), and b) thedownlink pCell. The pathloss reference for SCells in a pTAG may beconfigurable using RRC message(s) as a part of an SCell initialconfiguration and/or reconfiguration. According to some of the variousaspects of embodiments, a PhysicalConfigDedicatedSCell informationelement (IE) of an SCell configuration may include a pathloss referenceSCell (downlink carrier) for an SCell in a pTAG. The downlink SCelllinked to an uplink SCell using system information block 2 (SIB2) may bereferred to as the SIB2 linked downlink of the SCell. Different TAGs mayoperate in different bands. For an uplink carrier in an sTAG, thepathloss reference may be only configurable to the downlink SCell linkedto an uplink SCell using the system information block 2 (SIB2) of theSCell.

To obtain initial uplink (UL) time alignment for an sTAG, an eNB mayinitiate an RA procedure. In an sTAG, a UE may use one of any activatedSCells from this sTAG as a timing reference cell. In an exampleembodiment, the timing reference for SCells in an sTAG may be the SIB2linked downlink of the SCell on which the preamble for the latest RAprocedure was sent. There may be one timing reference and one timealignment timer (TAT) per TA group. A TAT for TAGs may be configuredwith different values. I n a MAC entity, when a TAT associated with apTAG expires: all TATs may be considered as expired, the UE may flushHARQ buffers of serving cells, the UE may clear any configured downlinkassignment/uplink grants, and the RRC in the UE may release PUCCH/SRSfor all configured serving cells. When the pTAG TAT is not running, ansTAG TAT may not be running. When the TAT associated with an sTAGexpires: a) SRS transmissions may be stopped on the correspondingSCells, b) SRS RRC configuration may be released, c) CSI reportingconfiguration for corresponding SCells may be maintained, and/or d) theMAC in the UE may flush the uplink HARQ buffers of the correspondingSCells.

An eNB may initiate an RA procedure via a PDCCH order for an activatedSCell. This PDCCH order may be sent on a scheduling cell of this SCell.When cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentinvention. An eNB transmits an activation command 600 to activate anSCell. A preamble 602 (Msg1) may be sent by a UE in response to a PDCCHorder 601 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 603 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 604 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding(configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may always be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements,to add, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. FIG. 10 is an example grouping of cells into PUCCHgroups as per an aspect of an embodiment of the present invention. Inthe example embodiments, one, two or more cells may be configured withPUCCH resources for transmitting CSI/ACK/NACK to a base station. Cellsmay be grouped into multiple PUCCH groups, and one or more cell within agroup may be configured with a PUCCH. In an example configuration, oneSCell may belong to one PUCCH group. SCells with a configured PUCCHtransmitted to a base station may be called a PUCCH SCell, and a cellgroup with a common PUCCH resource transmitted to the same base stationmay be called a PUCCH group.

In Release-12, a PUCCH can be configured on a PCell and/or a PSCell, butcannot be configured on other SCells. In an example embodiment, a UE maytransmit a message indicating that the UE supports PUCCH configurationon a PCell and SCell. Such an indication may be separate from anindication of dual connectivity support by the UE. In an exampleembodiment, a UE may support both DC and PUCCH groups. In an exampleembodiment, either DC or PUCCH groups may be configured, but not both.In another example embodiment, more complicated configurationscomprising both DC and PUCCH groups may be supported.

When a UE is capable of configuring PUCCH groups, and if a UE indicatesthat it supports simultaneous PUCCH/PUSCH transmission capability, itmay imply that the UE supports simultaneous PUCCH/PUSCH transmission onboth PCell and SCell. When multiple PUCCH groups are configured, a PUCCHmay be configured or not configured with simultaneous PUCCH/PUSCHtransmission.

In an example embodiment, PUCCH transmission to a base station on twoserving cells may be realized as shown in FIG. 10. A first group ofcells may employ a PUCCH on the PCell and may be called PUCCH group 1 ora primary PUCCH group. A second group of cells may employ a PUCCH on anSCell and may be called PUCCH group 2 or a secondary PUCCH group. One,two or more PUCCH groups may be configured. In an example, cells may begrouped into two PUCCH groups, and each PUCCH group may include a cellwith PUCCH resources. A PCell may provide PUCCH resources for theprimary PUCCH group and an SCell in the secondary PUCCH group mayprovide PUCCH resources for the cells in the secondary PUCCH group. Inan example embodiment, no cross-carrier scheduling between cells indifferent PUCCH groups may be configured. When cross-carrier schedulingbetween cells in different PUCCH groups is not configured, ACK/NACK onPHICH channel may be limited within a PUCCH group. Both downlink anduplink scheduling activity may be separate between cells belonging todifferent PUCCH groups.

A PUCCH on an SCell may carry HARQ-ACK and CSI information. A PCell maybe configured with PUCCH resources. In an example embodiment, RRCparameters for an SCell PUCCH Power Control for a PUCCH on an SCell maybe different from those of a PCell PUCCH. A Transmit Power Controlcommand for a PUCCH on an SCell may be transmitted in DCI(s) on theSCell carrying the PUCCH.

UE procedures on a PUCCH transmission may be different and/orindependent between PUCCH groups. For example, determination of DLHARQ-ACK timing, PUCCH resource determination for HARQ-ACK and/or CSI,Higher-layer configuration of simultaneous HARQ-ACK+CSI on a PUCCH,Higher-layer configuration of simultaneous HARQ-ACK+SRS in one subframemay be configured differently for a PUCCH PCell and a PUCCH SCell.

A PUCCH group may be a group of serving cells configured by a RRC anduse the same serving cell in the group for transmission of a PUCCH. APrimary PUCCH group may be a PUCCH group containing a PCell. A secondaryPUCCH group may be a PUCCH cell group not containing the PCell. In anexample embodiment, an SCell may belong to one PUCCH group. When oneSCell belongs to a PUCCH group, ACK/NACK or CSI for that SCell may betransmitted over the PUCCH in that PUCCH group (over PUCCH SCell orPUCCH PCell). A PUCCH on an SCell may reduce the PUCCH load on thePCell. A PUCCH SCell may be employed for UCI transmission of SCells inthe corresponding PUCCH group.

In an example embodiment, a flexible PUCCH configuration in whichcontrol signaling is sent on one, two or more PUCCHs may be possible.Beside the PCell, it may be possible to configure a selected number ofSCells for PUCCH transmission (herein called PUCCH SCells). Controlsignaling information conveyed in a certain PUCCH SCell may be relatedto a set of SCells in a corresponding PUCCH group that are configured bythe network via RRC signaling.

PUCCH control signaling carried by a PUCCH channel may be distributedbetween a PCell and SCells for off-loading or robustness purposes. Byenabling a PUCCH in an SCell, it may be possible to distribute theoverall CSI reports for a given UE between a PCell and a selected numberof SCells (e.g. PUCCH SCells), thereby limiting PUCCH CSI resourceconsumption by a given UE on a certain cell. It may be possible to mapCSI reports for a certain SCell to a selected PUCCH SCell. An SCell maybe assigned a certain periodicity and time-offset for transmission ofcontrol information. Periodic CSI for a serving cell may be mapped on aPUCCH (on the PCell or on a PUCCH-SCell) via RRC signaling. Thepossibility of distributing CSI reports, HARQ feedbacks, and/orScheduling Requests across PUCCH SCells may provide flexibility andcapacity improvements. HARQ feedback for a serving cell may be mapped ona PUCCH (on the PCell or on a PUCCH SCell) via RRC signaling.

In example embodiments, PUCCH transmission may be configured on a PCell,as well as one SCell in CA. An SCell PUCCH may be realized using theconcept of PUCCH groups, where aggregated cells are grouped into two ormore PUCCH groups. One cell from a PUCCH group may be configured tocarry a PUCCH. More than 5 carriers may be configured. In the exampleembodiments, up to n carriers may be aggregated. For example, n may be16, 32, or 64. Some CCs may have non-backward compatible configurationssupporting only advanced UEs (e.g. support licensed assisted accessSCells). In an example embodiment, one SCell PUCCH (e.g. two PUCCHgroups) may be supported. In another example embodiment, a PUCCH groupconcept with multiple (more than one) SCells carrying PUCCH may beemployed(e.g., there can be more than two PUCCH groups).

In an example embodiment, a given PUCCH group may not comprise servingcells of both MCG and SCG. One of the PUCCHs may be configured on thePCell. In an example embodiment, PUCCH mapping of serving cells may beconfigured by RRC messages. In an example embodiment, a maximum value ofan SCelllndex and a ServCelllndex may be 31 (ranging from 0 to 31). Inan example, a maximum value of stag-Id may be 3. The CIF for a scheduledcell may be configured explicitly. A PUCCH SCell may be configured bygiving a PUCCH configuration for an SCell. A HARQ feedback and CSIreport of a PUCCH SCell may be sent on the PUCCH of that PUCCH SCell.The HARQ feedback and CSI report of a SCell may sent on a PUCCH of aPCell if no PUCCH SCell is signaled for that SCell. The HARQ feedbackand CSI report of an SCell may be sent on the PUCCH of one PUCCH SCell;hence they may not be sent on the PUCCH of different PUCCH SCell. The UEmay report a Type 2 PH for serving cells configured with a PUCCH. In anexample embodiment, a MAC activation/deactivation may be supported for aPUCCH SCell. An eNB may manage the activation/deactivation status forSCells. A newly added PUCCH SCell may be initially deactivated.

In an example embodiment, independent configuration of PUCCH groups andTAGs may be supported. FIG. 11 and FIG. 12 show example configurationsof TAGs and PUCCH groups. For example, one TAG may contain multipleserving cells with a PUCCH. For example, each TAG may only comprisecells of one PUCCH group. For example, a TAG may comprise the servingcells (without a PUCCH) which belong to different PUCCH groups.

There may not be a one-to-one mapping between TAGs and PUCCH groups. Forexample, in a configuration, a PUCCH SCell may belong to primary TAG. Inan example implementation, the serving cells of one PUCCH group may bein different TAGs and serving cells of one TAG may be in different PUCCHgroups. Configuration of PUCCH groups and TAGs may be left to eNBimplementation. In another example implementation, restriction(s) on theconfiguration of a PUCCH cell may be specified. For example, in anexample embodiment, cells in a given PUCCH group may belong to the sameTAG. In an example, an sTAG may only comprise cells of one PUCCH group.I n an example, one-to-one mapping between TAGs and PUCCH groups may beimplemented. In implementation, cell configurations may be limited tosome of the examples. In other implementations, some or all the belowconfigurations may be allowed.

In an example embodiment, for an SCell in a pTAG, the timing referencemay be a PCell. For an SCell in an sTAG, the timing reference may be anyactivated SCell in the sTAG. For an SCell (configured with PUCCH or not)in a pTAG, a pathloss reference may be configured to be a PCell or anSIB-2 linked SCell. For an SCell in a sTAG, the pathloss reference maybe the SIB-2 linked SCell. When a TAT associated with a pTAG is expired,the TAT associated with sTAGs may be considered as expired. When a TATof an sTAG containing PUCCH SCell expires, the MAC may indicate to anRRC to release PUCCH resource for the PUCCH group. When the TAT of ansTAG containing a PUCCH SCell is not running, the uplink transmission(PUSCH) for SCells in the secondary PUCCH group not belonging to thesTAG including the PUCCH SCell may not be impacted. The TAT expiry of ansTAG containing a PUCCH SCell may not trigger TAT expiry of other TAGsto which other SCells in the same PUCCH group belong. When the TATassociated with sTAG not containing a PUCCH SCell is not running, thewireless device may stop the uplink transmission for the SCell in thesTAG and may not impact other TAGs.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

Example embodiments of the invention may enable operation of multiplePUCCH groups. Other example embodiments may comprise a non-transitorytangible computer readable media comprising instructions executable byone or more processors to cause operation of PUCCH groups. Yet otherexample embodiments may comprise an article of manufacture thatcomprises a non-transitory tangible computer readable machine-accessiblemedium having instructions encoded thereon for enabling programmablehardware to cause a device (e.g. wireless communicator, UE, basestation, etc.) to enable operation of PUCCH groups. The device mayinclude processors, memory, interfaces, and/or the like. Other exampleembodiments may comprise communication networks comprising devices suchas base stations, wireless devices (or user equipment: UE), servers,switches, antennas, and/or the like. In an example embodiment one ormore TAGs may be configured along with PUCCH group configuration.

FIG. 13 is an example MAC PDU as per an aspect of an embodiment of thepresent invention. In an example embodiment, a MAC PDU may comprise of aMAC header, zero or more MAC Service Data Units (MAC SDU), zero or moreMAC control elements, and optionally padding. The MAC header and the MACSDUs may be of variable sizes. A MAC PDU header may comprise one or moreMAC PDU subheaders. A subheader may correspond to either a MAC SDU, aMAC control element or padding. A MAC PDU subheader may comprise headerfields R, F2, E, LCID, F, and/or L. The last subheader in the MAC PDUand subheaders for fixed sized MAC control elements may comprise thefour header fields R, F2, E, and/or LCID. A MAC PDU subheadercorresponding to padding may comprise the four header fields R, F2, E,and/or LCID.

In an example embodiment, LCID or Logical Channel ID field may identifythe logical channel instance of the corresponding MAC SDU or the type ofthe corresponding MAC control element or padding. There may be one LCIDfield for a MAC SDU, MAC control element or padding included in the MACPDU. In addition to that, one or two additional LCID fields may beincluded in the MAC PDU when single-byte or two-byte padding is requiredbut cannot be achieved by padding at the end of the MAC PDU. The LCIDfield size may be, e.g. 5 bits. L or the Length field may indicate thelength of the corresponding MAC SDU or variable-sized MAC controlelement in bytes. There may be one L field per MAC PDU subheader exceptfor the last subheader and subheaders corresponding to fixed-sized MACcontrol elements. The size of the L field may be indicated by the Ffield and F2 field. The F or the Format field may indicate the size ofthe Length field. There may be one F field per MAC PDU subheader exceptfor the last subheader and subheaders corresponding to fixed-sized MACcontrol elements and expect for when F2 is set to 1. The size of the Ffield may be 1 bit. In an example, if the F field is included, and/or ifthe size of the MAC SDU or variable-sized MAC control element is lessthan 128 bytes, the value of the F field is set to 0, otherwise it isset to 1. The F2 or the Format2 field may indicate the size of theLength field. There may be one F2 field per MAC PDU subheader. The sizeof the F2 field may be 1 bit. In an example, if the size of the MAC SDUor variable-sized MAC control element is larger than 32767 bytes and ifthe corresponding subheader is not the last subheader, the value of theF2 field may be set to 1, otherwise it is set to 0. The E or theExtension field may be a flag indicating if more fields are present inthe MAC header or not. The E field may be set to “1” to indicate anotherset of at least R/F2/E/LCID fields. The E field may be set to “0” toindicate that either a MAC SDU, a MAC control element or padding startsat the next byte. R or reserved bit, set to “0”.

MAC PDU subheaders may have the same order as the corresponding MACSDUs, MAC control elements and padding. MAC control elements may beplaced before any MAC SDU. Padding may occur at the end of the MAC PDU,except when single-byte or two-byte padding is required. Padding mayhave any value and the MAC entity may ignore it. When padding isperformed at the end of the MAC PDU, zero or more padding bytes may beallowed. When single-byte or two-byte padding is required, one or twoMAC PDU subheaders corresponding to padding may be placed at thebeginning of the MAC PDU before any other MAC PDU subheader. In anexample, a maximum of one MAC PDU may be transmitted per TB per MACentity, a maximum of one MCH MAC PDU can be transmitted per TTI.

At least one RRC message may provide configuration parameters for atleast one cell and configuration parameters for PUCCH groups. Theinformation elements in one or more RRC messages may provide mappingbetween configured cells and PUCCH SCells. Cells may be grouped into aplurality of cell groups and a cell may be assigned to one of theconfigured PUCCH groups. There may be a one-to-one relationship betweenPUCCH groups and cells with configured PUCCH resources. At least one RRCmessage may provide mapping between an SCell and a PUCCH group, andPUCCH configuration on PUCCH SCell.

System information (common parameters) for an SCell may be carried in aRadioResourceConfigCommonSCell in a dedicated RRC message. Some of thePUCCH related information may be included in common information of anSCell (e.g. in the RadioResourceConfigCommonSCell). Dedicatedconfiguration parameters of SCell and PUCCH resources may be configuredby dedicated RRC signaling using, for example,RadioResourceConfigDedicatedSCell.

The IE PUCCH-ConfigCommon and IE PUCCH-ConfigDedicated may be used tospecify the common and the UE specific PUCCH configuration respectively.

In an example, PUCCH-ConfigCommon may include: deltaPUCCH-Shift:ENUMERATED {ds1, ds2, ds3}; nRB-CQI: INTEGER (0..98); nCS-AN: INTEGER(0..7); and/or n1PUCCH-AN: INTEGER (0..2047). The parameterdeltaPUCCH-Shift (Δ_(shift) ^(PUUCH)), nRB-CQI (N_(RB) ⁽²⁾), nCS-An(N_(cs) ⁽¹⁾), and n1PUCCH-AN (N_(PUCCH) ⁽¹⁾) may be physical layerparameters of PUCCH.

PUCCH-ConfigDedicated may be employed. PUCCH-ConfigDedicated mayinclude: ackNackRepetition CHOICE{release: NULL, setup: SEQUENCE{repetitionFactor: ENUMERATED {n2, n4, n6, sparel},n1PUCCH-AN-Rep:INTEGER (0..2047)}}, tdd-AckNackFeedbackMode: ENUMERATED {bundling,multiplexing} OPTIONAL}. ackNackRepetition j parameter indicates whetherACK/NACK repetition is configured. n2 corresponds to repetition factor2, n4 to 4 for repetitionFactor parameter (N_(ANRep)). n1PUCCH-AN-Repparameter may be n_(PUCCH, ANRep) ^((1,p)) for antenna port P0 and forantenna port P1. dd-AckNackFeedbackMode parameter may indicate one ofthe TDD ACK/NACK feedback modes used. The value bundling may correspondto use of ACK/NACK bundling whereas, the value multiplexing maycorrespond to ACK/NACK multiplexing. The same value may apply to bothACK/NACK feedback modes on PUCCH as well as on PUSCH.

The parameter PUCCH-ConfigDedicated may include simultaneous PUCCH-PUSCHparameter indicating whether simultaneous PUCCH and PUSCH transmissionsis configured. An E-UTRAN may configure this field for the PCell whenthe nonContiguousUL-RA-WithinCC-Info is set to supported in the band onwhich PCell is configured. The E-UTRAN may configure this field for thePSCell when the nonContiguousUL-RA-WithinCC-Info is set to supported inthe band on which PSCell is configured. The E-UTRAN may configure thisfield for the PUCCH SCell when the nonContiguousUL-RA-WithinCC-Info isset to supported in the band on which PUCCH SCell is configured.

A UE may transmit radio capabilities to an eNB to indicate whether UEsupport the configuration of PUCCH groups. The simultaneous PUCCH-PUSCHin the UE capability message may be applied to both a PCell and anSCell. Simultaneous PUCCH+PUSCH may be configured separately (usingseparate IEs) for a PCell and a PUCCH SCell. For example, a PCell and aPUCCH SCell may have different or the same configurations related tosimultaneous PUCCH+PUSCH.

The eNB may select the PUCCH SCell among current SCells or candidateSCells considering cell loading, carrier quality (e.g. using measurementreports), carrier configuration, and/or other parameters. From afunctionality perspective, a PUCCH Cell group management procedure mayinclude a PUCCH Cell group addition, a PUCCH cell group release, a PUCCHcell group change and/or a PUCCH cell group reconfiguration. The PUCCHcell group addition procedure may be used to add a secondary PUCCH cellgroup (e.g., to add PUCCH SCell and one or more SCells in the secondaryPUCCH cell group). In an example embodiment, cells may be released andadded employing one or more RRC messages. In another example embodiment,cells may be released employing a first RRC message and then addedemploying a second RRC messages.

SCells including PUCCH SCell may be in a deactivated state when they areconfigured. A PUCCH SCell may be activated after an RRC configurationprocedure by an activation MAC CE. An eNB may transmit a MAC CEactivation command to a UE. The UE may activate an SCell in response toreceiving the MAC CE activation command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

LTE-Advanced introduced Carrier Aggregation (CA) in Release-10. InRelease-10 CA, the Primary Cell (PCell) is always activated. One or moreSecondary Cells (SCells) can be in activated or deactivated state. TheSCell activation/deactivation processes were introduced in Release-10 toachieve battery power savings. When an SCell is deactivated, the UE maystop receiving downlink signals and stop transmission on the SCell. InRelease-10 CA, the default state of an SCell is deactivated when theSCell has been configured/added. Additional activation procedureemploying MAC CE Activation Command may be needed to activate the SCell.SCells may be deactivated either by an activation/deactivation MAC CE orby the sCellDeactivationTimer. The UE and eNB maintain onesCellDeactivationTimer per SCell with a common value across SCells. eNBmaintains the activation/deactivation status of an SCell for a wirelessdevice.

In LTE-Advanced Release-12, Dual Connectivity (DC) was introduced. InDC, UE maintains connectivity to a Master eNB (MeNB) and a Secondary eNB(SeNB). Serving cells may be grouped into cell groups (CGs) such as amaster CG (MCG) and a secondary CG (SCG). The primary cell in MeNB iscalled PCell. A cell in SeNB is called PSCell. A PSCell may supportsimilar functions supported by a PCell, such as PUCCH, RACH, RLM, etc.If PSCell is deactivated, many processes may be impacted in SCG, e.g.RACH and PUCCH delivery. Therefore, in Release-12 DC, PSCell in SCG andPCell in MCG are kept in the activated state. In DC, theactivation/deactivation processes may be performed per CG and per eNB.Activation/deactivation related information may not be exchanged betweenMeNB and SeNB. With DC, the cells with PUCCH (e.g. PCell and PSCell) arealways in an activated state after they are configured. This process mayprevent the need for cross-eNB activation/deactivation.

Cells of an eNB may be grouped in multiple PUCCH groups, each having itsown PUCCH resources on a PUCCH SCell. An eNB configures PUCCH groups fora wireless device by transmitting RRC message(s) to the wireless device.Implementation of activation/deactivation processes for PUCCH SCell maypresent some issues, if Release-10 or 12 activation/deactivationprocesses are implemented. For example, it may be needed to implementmethods and systems to handle PUCCH transmissions when PUCCH SCell isdeactivated and one or more SCells in the corresponding PUCCH group arestill active. Novel PUCCH SCell activation/deactivation procedures maybe implemented when PUCCH SCell is configured. In addition, novel PUCCHSCell activation/deactivation procedures may be implemented to handlescenarios wherein PUCCH is deactivated.

PUCCH SCell may include many of the functionalities of the PSCell. Someof the issues related to deactivation of PUCCH SCell may be resolved ifPUCCH SCell is always kept active, like, PCell or PSCell in priorreleases of LTE-Advanced. Such a solution may increase battery powerconsumption in the UE since the UE has to always keep PUCCH SCellactivated after PUCCH SCell is configured.

Implementation of the same activation and deactivation processes forPUCCH SCell and PSCell in DC may result in an inefficientimplementation. To achieve battery power saving benefits similar to theexisting CA technology, it may be beneficial to enable deactivation ofthe PUCCH SCell. PUCCH SCell delivers uplink control information for theserving cells in the corresponding PUCCH cell group using its configuredPUCCH resources. When there is no need for PUCCH UCI delivery, e.g. whenother serving cells in the same PUCCH cell group are deactivated, thePUCCH SCell may be deactivated. Support for activation/deactivation ofPUCCH SCell may provide battery power saving benefits. There may be noneed to keep PUCCH SCell activated all the time, for example when thereis no data transmission on cells in the corresponding PUCCH group. APUCCH SCell deactivation procedure may introduce new implications forSCells that are in the corresponding PUCCH group. It may be beneficialto avoid or reduce situations where an active SCell may not have accessto an activated PUCCH SCell. It may be beneficial to develop systems andprocesses wherein the PUCCH SCell may be activated/deactivated to reducebattery power consumption in the UE. Implementations may consider thatthe PUCCH SCell carries control information related to other SCellswithin the corresponding PUCCH group.

Solutions may be provided in which PUCCH control information such asHARQ/CQI/SR may be sent on the PUCCH SCell even when the PUCCH SCell isdeactivated. Allowing transmission of the PUCCH control information on adeactivated PUCCH SCell may require that PUCCH SCell to be capable oftransmitting uplink signals when it is deactivated, or may requireactivation of PUCCH SCell when such transmissions are needed. Such asolution may to be too complex to implement and may require many changesto existing physical and MAC layer procedures and/or hardware. Partiallyactivating the PUCCH SCell for transmission of PUCCH control informationmay increase power consumption and transceiver complexity and may not bedesirable.

Example embodiments of the invention describe solutions that provideefficient systems and processes for PUCCH SCell activation/deactivationprocess in an LTE network, eNB and UE. The example embodiments provideefficient mechanisms for the network, eNB and UE to implement activationand deactivation processes for SCells. This may require enhancements toexisting eNB and UE processes. The embodiments may add additionalrequirements in eNB and UE implementations and may reduce battery powerconsumption, without adding too much complexity in eNB and UEimplementations.

In an example embodiment of the invention, if the MAC entity isconfigured with one or more SCells, the network may activate anddeactivate the configured SCells. The SpCell may always be activatedwhen it is configured. The network may activate and deactivate theSCell(s) by sending the Activation/Deactivation MAC control element.Furthermore, the MAC entity may maintain a sCellDeactivationTimer timerfor a configured SCell. The same initial timer value applies to aninstance of the sCellDeactivationTimer and it is configured by RRC. Theconfigured SCells may be initially deactivated upon addition and after ahandover.

In an example embodiment, when PUCCH SCell is configured by the RRClayer, the initial state of the PUCCH SCell may be a deactivated state.An eNB may activate a PUCCH SCell when it is needed by transmitting aMAC Activation CE. In an example embodiment, when PUCCH SCell isdeactivated, PUCCH resource configuration may be kept (and notreleased). The configuration of the corresponding PUCCH group may bemaintained while deactivating PUCCH SCell or other SCells in the PUCCHgroup. The re-activation of PUCCH transmission after a deactivation maynot require additional RRC reconfiguration procedure since RRCConfiguration of PUCCH SCell is retained when it is deactivated. In someembodiments, if the TAG including PUCCH SCell is expired, PUCCH may bereleased and RRC reconfiguration may be needed to reconfigure PUCCHresources on PUCCH SCell.

SCell activation/deactivation process was introduced in LTE-Advancedrelease-10 and beyond. If the MAC entity is configured with one or moreSCells, the network may activate and deactivate the configured SCells.The SpCell may always be activated. The network may activate anddeactivate the SCell(s) by sending one or more ofActivation/Deactivation MAC control elements. The MAC entity maymaintain a sCellDeactivationTimer timer per configured SCell and maydeactivate the associated SCell upon its expiry. The same initial timervalue may apply to each instance of the sCellDeactivationTimer and it isconfigured by RRC. An sCellDeactivationTimer IE is included inMac-MainConfig dedicated parameter in an RRC message. The configuredSCells initially be deactivated upon addition and after a handover.

Various implementation of the Activation/Deactivation MAC controlelement may be possible. In an example embodiment, theActivation/Deactivation MAC control element is identified by a MAC PDUsubheader with a pre-assigned LCID. It may have a fixed size andcomprise one or more octets containing C-fields and one or moreR-fields. The activation/deactivation MAC control element may be definedas follows. Ci: if there is an SCell configured with SCelllndex i asspecified in, this field indicates the activation/deactivation status ofthe SCell with SCelllndex i, else the MAC entity may ignore the Cifield. The Ci field is set to “1” to indicate that the SCell withSCelllndex i may be activated. The Ci field is set to “0” to indicatethat the SCell with SCelllndex i may be deactivated; R: Reserved bit,set to “0”. Other embodiments may be implemented. For example, when UEis configured with more than 5 or 7 carriers, the format may includemore than one byte including a longer bitmap.

Various deactivation timer management processes may be implemented. Inan example embodiment, if PDCCH on the activated SCell indicates anuplink grant or downlink assignment; or if PDCCH on the Serving Cellscheduling the activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell: the UE may restart thesCellDeactivationTimer associated with the SCell. Other examplesCellDeactivationTimer embodiments may also be implemented. Adeactivation timer of a PUCCH SCell may be disabled.

In the current LTE-Advanced transceiver operation, the MAC entity mayfor each TTI and for each configured SCell perform certain functionsrelated to activation/deactivation of SCell(s). If the MAC entityreceives an activation/deactivation MAC control element in this TTIactivating the SCell, the MAC entity may in the TTI according to anactivation timing, activate the SCell; start or restart thesCellDeactivationTimer associated with the SCell; and trigger PHR (powerheadroom). If the MAC entity receives an activation/deactivation MACcontrol element in this TTI deactivating the SCell; or if thesCellDeactivationTimer associated with the activated SCell expires inthis TTI: in the TTI according to a deactivation timing; stop thesCellDeactivationTimer associated with the SCell; and/or flush all HARQbuffers associated with the SCell.

If the SCell is deactivated a UE may perform the following actions: nottransmit SRS on the SCell; not report CQI/PMI/RI/PTI for the SCell; nottransmit on UL-SCH on the SCell; not transmit on RACH on the SCell; notmonitor the PDCCH on the SCell; not monitor the PDCCH for the SCell.When SCell is deactivated, the ongoing Random Access procedure on theSCell, if any, is aborted.

3GPP Technical Specification number TS 36.213: “Evolved UniversalTerrestrial Radio Access (E-UTRA); Physical Layer Procedures” addressesthe timing for secondary cell activation/deactivation. Section 4.3 of3GPP TS 36.213 V11.2.0 (2013-02) (Release 11) describes that when a UEreceives a MAC activation command for a secondary cell in subframe n,the corresponding actions in the MAC layer shall be applied in subframen+8. When a UE receives a MAC deactivation command for a secondary cellor a secondary cell's deactivation timer expires in subframe n, thecorresponding actions in the MAC layer shall apply no later thansubframe n+8, except for the actions related to CSI reporting whichshall be applied in subframe n+8.

Due to some timing issues with the requirements defined in 3GPP TS36.213 V11.2.0 (2013-02) (Release 11), section 4.3 was updated in thesubsequent release. Section 4.3 of 3GPP TS 36.213 (in all releases fromV11.3.0/2013-02 to V12.4/2014-12: the most recent release) relaxes someof the timing requirements for the UE. The updated section 4.3 describesthat when a UE receives a MAC activation command for a secondary cell insubframe n, the corresponding actions in the MAC layer shall be appliedno later than the minimum requirement defined in 3GPP TS 36.133 and noearlier than subframe n+8, except for the following: the actions relatedto CSI reporting and the actions related to the sCellDeactivationTimerassociated with the secondary cell, which shall be applied in subframen+8. When a UE receives a MAC deactivation command for a secondary cellor the sCellDeactivationTimer associated with the secondary cell expiresin subframe n, the corresponding actions in the MAC layer shall apply nolater than the minimum requirement defined in 3GPP TS 36.133, except forthe actions related to CSI reporting which shall be applied in subframen+8.3GPP TS 36.133 describes the SCell activation delay requirement fora deactivated SCell. Deactivation delay may take longer than 8 msecdepending on a UE conditions with respect to the SCell.

The current LTE-Advanced specifications requires that when a UE receivesa MAC activation command for a secondary cell in subframe n, the actionsrelated to CSI reporting and the actions related to thesCellDeactivationTimer associated with the secondary cell, are appliedin subframe n+8. The current LTE-Advanced specifications requires thatwhen a UE receives a MAC deactivation command for a secondary cell orother deactivation conditions are met (e.g. the sCellDeactivationTimerassociated with the secondary cell expires) in subframe n, the actionsrelated to CSI reporting are applied in subframe n+8.

In the current LTE-Advanced transceiver operations when a UE receives aMAC activation command for an SCell in subframe n, the UE startsreporting CQI/PMI/RI/PTI for the SCell at subframe n+8 and starts orrestarts the sCellDeactivationTimer associated with the SCell atsubframe n+8. It is important to define the timing of these actions forboth UE and eNB. For example, sCellDeactivationTimer is maintained inboth eNB and UE and it is important that both UE and eNB stop, startand/or restart this timer in the same TTI. Otherwise, thesCellDeactivationTimer in the UE may not be in-sync with thecorresponding sCellDeactivationTimer in the eNB. Also eNB startsmonitoring and receiving CSI (CQI/PMI/RI/PTI) according to thepredefined timing in the same TTI and/or after UE starts transmittingthe CSI. If the CSI timings in UE and eNB are not coordinated based on acommon standard or air interface signaling the network operation mayresult in inefficient operations and/or errors. CSI may include, e.g.,channel quality indicator (CQI), preceding matrix indicator (PMI),and/or rank indicator (RI).

An example CQI indices and their interpretations are given in FIG. 14A(Table 1) for reporting CQI based on QPSK, 16QAM and 64QAM. An exampleCQI indices and their interpretations are given in FIG. 14B (Table 2)for reporting CQI based on QPSK, 16QAM, 64QAM and 256QAM. These tablesare for example only and other tables may be developed for providing CQIfeedback. In an example embodiment, based on an unrestricted observationinterval in time and frequency, the UE may derive for each CQI valuereported in uplink subframe n the highest CQI index between 1 and 15 inTable 1 or Table 2 which satisfies the following condition, or CQI index0 if CQI index 1 does not satisfy the condition: a single PDSCHtransport block with a combination of modulation scheme and transportblock size corresponding to the CQI index, and occupying a group ofdownlink physical resource blocks termed the CSI reference resource,could be received with a transport block error probability not exceeding0.1.

In an example embodiment, when a UE transmits/reports CQI or in generalCSI to the base station, the UE may transmit a valid or invalid CSI. Forexample, a UE may transmit a CQI index of 0, which indicates an out ofrange value. In the example embodiments, when it is indicated that theUE transmits CSI it refers to transmission of a valid or invalid CSI,and/or in range or out of range CSI. When explicit transmission of validor invalid CSI is intended, it is explicitly indicated that valid orinvalid CSI is transmitted. In an example embodiment, a UE may initiallytransmit invalid CSI until UE successfully detects and is able tomeasure CSI for a given cell. When an eNB receives an invalid CSI, theeNB may take a proper action according to its implementation. In anexample, when a UE is unable to measure a downlink signal, it may reportan invalid CQI. In an example, when a UE obtain a measurement of adownlink signal below a threshold, it may report an invalid CQI.

FIGS. 15A and 15B are example diagrams illustrating timing of differentevents according to the current LTE-Advanced transceivers. The MACentity receives the Activation MAC CE activating the SCell (e.g.Activation/Deactivation MAC CE activating the SCell) in subframe (TTI)n. The MAC entity starts or restarts the sCellDeactivationTimerassociated with the SCell in subframe n+8. The MAC entity startsreporting CSI (CQI/PMI/RI/PTI) reporting for the SCell in subframe n+8.Other activation actions listed below (if configured) are applied nolater than the minimum defined delay requirement and no earlier thansubframe n+8. Other actions include one or many of the following: SRStransmissions on the SCell; PDCCH monitoring on the SCell; PDCCHmonitoring for the SCell; trigger PHR. For example, the other actionsmay be applied in subframe n+8 or later at subframe n+12, n+13, or n+k,wherein k is a number between 0 and an upper limit which ispre-defined/pre-configured for certain scenarios. Other actionsnecessarily do not need to happen in the same subframe. An example upperlimit for k is described below.

In an example scenario, when a secondary cell activation MAC CE inreceived in subframe n, the UE may be able to transmit uplink signalsfor the secondary cell on or before subframe n+24 provided the followingconditions are met for the SCell:

During the period equal to max(5 measCycleSCell, 5 DRX cycles) beforethe reception of the SCell activation command:

the UE has sent a valid measurement report for the SCell being activatedand

the SCell being activated remains detectable according to a cellidentification conditions,

SCell being activated also remains detectable during the SCellactivation delay according to the cell identification conditions.

Otherwise upon receiving the SCell activation command in subframe n, theUE may be capable to transmit valid CSI report and apply other actionsrelated to the activation command for the SCell being activated no laterthan in subframe n+34 provided the SCell can be successfully detected onthe first attempt.

In an example embodiment, while activating an SCell if any other SCellis activated, deactivated, configured and/or deconfigured by the UE thenthe UE activation delay may increase. For example, the increase inactivation delay may depend on the number of times the other one or moreSCells are activated, deactivated, configured or deconfigured while theSCell is being activated.

If there is no reference signal received for the CSI measurement overthe delay corresponding to the minimum requirements specified above,then the UE may report corresponding valid CSI for the activated SCellon the next available uplink reporting resource after receiving thereference signal.

If there are no uplink resources for reporting the valid CSI in subframen+24 or n+34 then the UE may use the next available uplink resource forreporting the corresponding valid CSI.

The valid CSI is based on the UE measurement and corresponds to any CQIvalue with the exception of CQI index=0 (out of range) provided: certainconditions are met over the entire SCell activation delay and theconditions defined for CQI reporting are met. In addition to CSIreporting defined above, UE may also apply other actions related to theactivation command specified in for an SCell at the first opportunitiesfor the corresponding actions once the SCell is activated.

In practice a UE may have shorter or longer deactivation delay than theminimum requirement specified above depending on the transceiver state,air interface quality, etc. Activation delay may depend on when adetection attempt, by a UE (wireless device), for the secondary cell issuccessful. The UE may have a shorter UE SCell activation delay than theUE SCell activation delay described above depending on air interface andUE conditions. The UE and/or the network may benefit from reduced SCellactivation delay by the UE.

To activate an SCell, the UE may need to acquire PSS/SSS (sync signals)signals, if synchronization signals are not acquired. In an exampleembodiment, there may the following different scenarios for the SCellactivation: a) cold-start 1: SCell RF is not activated; timinginformation is unknown; not possible for intraband contiguous CA, b)cold-start 2 SCell RF is not activated; timing information is known, c)warm-start: RF is already active; and timing information is known. Forexample, the maximum allowed activation time for cold-start 2, where anSCell RF chain is not activated, but SCell timing information is known,may be 24 ms. 4 ms may be needed for UE to decode an activation command(MAC control element) and transmit ACK, and 20 ms may be needed for RFwarm-up, AGC settling, and frequency and time tracking loops warm-up. RFwarm-up and AGC settling may be achieved within a few milliseconds (<4ms) or an even shorter time period by applying additional technique.

Currently, the MAC entity receives the activation MAC CE activating theSCell (e.g. activation/deactivation MAC CE activating the SCell). TheMAC entity start or restart the sCellDeactivationTimer associated withthe SCell in subframe n+8. The MAC entity starts reporting CSI(CQI/PMI/RI/PTI) reporting for the SCell in subframe n+8 no matterwhether the secondary cell is properly acquired or not.

As illustrated in the example FIG. 15A, the UE may start reportinginvalid/out-of-range CSI for the SCell until valid CSI is available. Asshown in example FIG. 15B, UE starts reporting valid CSI in subframen+8+k, wherein k depends on when a valid CSI is available. Starting timefor CQI report transmission does not depend on different UEimplementation. This enhances PUCCH decoding process on PCell. Minimumrequirement of when valid CQI result is send is specified. As discussed,the UE may exceed the minimum requirement in some scenarios. Suchprobability may be reduced as much as possible. In an exampleembodiment, if CQI report is configured, out of range CQI/CSI may bereported before the UE is able to perform CSI measurement for the SCell.The UE may be able to transmit valid CSI no later than subframe n+24[+X]for Transmission Modes (TM) other than TM9 and 4 ms after the firstCSI-RS subframe since n+24[+X] for TM9. X may be a predefined parameter,for example, may be equal to 10.

There could be a certain period that the UE does not have valid CQIresults for an SCell upon the activation of the SCell. The period maydepend on when the UE successfully detects the cell and/or when the UEstarts CQI measurement which may vary depending on the air interfacecondition, signal (e.g. CSI RS) timings and/or UE implementation.Starting time for CQI report transmission does not depend on differentUE implementations. The UE may start reporting CQI from subframe n+8 anda fixed value (e.g. out of range) may be reported when there are novalid CQI results available for the SCell. This would reduce thepossibility that CQI size uncertainty complicates the eNB decoding ofuplink channel. A timing requirement may be set when the UE has validCQI results for the SCell at the latest after activation. A UEimplementation may reduce the probability of exceeding this timingrequirement.

FIG. 15B shows another example when UE has a shorter activation delayand valid CSI are available. The UE may start reporting a valid CSIstarting subframe n+8.

When a UE starts reporting CSI in subframe n+8, it does not necessarilyimply that UE transmits CSI in subframe n+8. The UE may transmit CSI inthe first available CSI resources allocated to UE starting subframe n+8.For example, the UE may transmit the first CSI in subframe n+8, n+10,etc. depending on when the first available CSI resource is available.

Some example embodiments of the invention improves the signal timings ofFIGS. 15A and 15B to enhance CSI and other uplink control signalingtransmission mechanisms when at least one PUCCH SCell is configured.

FIGS. 16A and 16B are example diagrams illustrating timing of someevents when an SCell is deactivated as per an aspect of an embodiment ofthe present invention. In an example scenario, a UE may deactivate theSCell because the MAC entity receives an Activation/Deactivation MACcontrol element in this TTI n deactivating the SCell. In another examplescenario, UE may deactivate the SCell because the sCellDeactivationTimerassociated with the activated SCell expires in TTI n. As shown in FIGS.16A and 16B, the UE stops reporting CSI in the subframe n+8. The UE mayperform other deactivation tasks in any of the subframes n to n+8 (n+p,wherein p is an integer number between 0 to 8). Other deactivation tasksmay include any of the following: stop the sCellDeactivationTimerassociated with the SCell; flush HARQ buffers associated with the SCell;not transmit SRS on the SCell; not transmit on UL-SCH on the SCell; nottransmit on RACH on the SCell; not monitor the PDCCH on the SCell; notmonitor the PDCCH for the SCell.

The current timing of certain actions (e.g. CSI reporting andsCellDeactivationTimer management) results in complex transceiverdesign, inefficient operations, and/or errors when support for PUCCH onsecondary cell(s) is introduced in LTE-Advanced as discussed in thisspecifications. Example embodiments of the invention addresses issuesrelated to activation timing in a wireless device and wireless network.Example embodiments of the invention improve the current LTE-Advancedtransceivers and enhance activation and deactivation mechanisms in anLTE-advanced transceiver.

Example embodiments of the invention provide improvements to the currentactivation and deactivation timings in an LTE-Advanced transceiver in awireless device and/or a wireless network. Timing of one or more actionsin an LTE-Advanced transceiver in a wireless device and/or a wirelessnetwork is updated to improve network and/or wireless device performanceand reduce or prevent unwanted conditions.

Cells of an eNB may be grouped in multiple PUCCH groups. A PUCCH groupmay have its PUCCH resources on a PUCCH SCell. An eNB configures PUCCHgroups for a wireless device by transmitting RRC messages to thewireless device. Implementation of activation/deactivation processes fora PUCCH SCell may present some issues, if Release-10 or 12activation/deactivation processes are implemented. Novel SCellactivation/deactivation procedures may be implemented when PUCCH SCellis activated and/or deactivated.

In an example embodiment of the invention, when a UE receives a MACactivation command for an SCell in subframe n, the UE starts or restartsthe sCellDeactivationTimer associated with the SCell at subframe n+8.The requirements for the start time to report CQI/PMI/RI/PTI for theSCell may not be restricted to subframe n+8.

In the example embodiments, the fixed delay of 8 subframes, is used forrestarting sCellDeactivationTimer and many other actions. One mayimplements other fixed delays instead of 8 subframes for restartingsCellDeactivationTimer and many other actions, without deviating fromthe invention. For example, fixed delays of 4, 6, 10, 12, etc. subframesmay be employed.

In the example embodiments, it is considered that when a PUCCH SCell isactivated in a TAG, the TAG is uplink synchronized. For example PUCCHSCell may be activated in a pTAG or an uplink synchronized sTAG. FIG. 17shows example diagrams illustrating timing of some events according toan example embodiment of the invention. In the example embodiment of theinvention, when a UE receives a MAC activation command for a PUCCH SCellin subframe n, the UE starts or restarts the sCellDeactivationTimerassociated with the PUCCH SCell at subframe n+8. The requirements forthe start time to report CQI/PMI/RI/PTI for the SCell may not berestricted to subframe n+8. Depending on the state of the UE, airinterface quality, and UE implementation, UE may acquire the PUCCH SCellany time after subframe n.

In an example embodiment, transmission of uplink CSI may start atsubframe n+8+k (e.g. k greater or equal to 0). The parameter k maydepend, at least, on when a detection attempt, by the wireless device,for the PUCCH SCell is successful. The parameter k may depend on theactivation delay of the PUCH SCell. When the UE successfully detectedthe PUCCH SCell and the UE is ready for uplink transmission on the PUCCHSCell, the UE may start transmission of PUCCH at subframe n+8+k and inthe first available PUCCH resource. In an example scenario, the UE mayfirst transmit a fixed CSI (e.g. invalid or out of range CSI) if nomeasurement is available or a measurement of a downlink signal is belowa threshold. The UE detects the PUCCH SCell and may be able to transmituplink signals including PUCCH CSI signals. After the PUCCH SCell isdetected, the UE starts measuring the CSI. The CSI measurement may takea couple of subframes. Then the UE may transmit a measured CSI (e.g.valid CSI) when air interface measurement information for the PUCCHSCell is available. In an example scenario, the UE may detect the PUCCHbefore subframe n+8 and measure the CSI before n+8, then the UE maystart transmission of the measured CSI (e.g. valid CSI) at subframe n+8.This, for example, may happen when the UE is already synchronized withthe UE and can quickly measure CSI of the PUCCH SCell.

The activation of the PUCCH secondary cell is considered completed insubframe i, when the PUCCH secondary cell becomes capable oftransmitting CSI in subframe i+1. When the PUCCH secondary cell iscapable of transmitting CSI in subframe i+1 and starts transmitting CSIfrom subframe i+1, it implies that the UE transmits CSI in the firstavailable CSI resources on PUCCH SCell on or after subframe i+1.

Detection and/or CSI measurement period may be random and depends onmany factors. The UE may make multiple detection attempts until itsuccessfully detects the PUCCHS Cell. A UE implementation may detect thePUCCHS Cell and start measuring earlier than n+8, even before n+4. Ifmeasurements are started before n+4, the UE may have a valid CQI resultat n+8, and may be ready to send CQI at n+8. For example, CRS for CQImeasurement may be available every TTI for some transmission modes. ForTM9 where CQI measurement is based on CSI RS with configurableperiodicity e.g. 5-80 ms, it is possible that the period without validCQI is much longer than 4 ms in case the UE miss the CSI RS occasion.The period may be as long as until the first subframe has CSI RSavailable+4 ms considering UE processing time for CQI measurement. Thetime point when the UE have valid CQI result may depend on transmissionmode and CSI RS configuration.

In an example embodiment, transmission of uplink CSI may start atsubframe n+8+k depending, at least, on when a detection attempt, by thewireless device, for the PUCCH SCell is successful and CSI measurementis available. The CSI starting subframe may depend, at least in part, onwhen a UE successfully measured the air interface signal and is ready totransmit a CSI (e.g. valid CSI). The UE may start transmission of CSI atsubframe n+k+8.

The parameter k is variable and indicates the number of subframes aftersubframe n+8 when UE starts CSI transmission. The parameter k may dependon the state of the UE, air interface quality, UE implementation, and/orCSI measurement.

In a different scenario, for example, when the PUCCH detection takeslonger than certain period, for example, longer than 40, 50, 70subframes (these are example ranges and are not limiting). This mayhappen when the air interface signal quality is low, the UE starts froma cold start, the UE makes multiple detection attempts, and/or any otherUE or system implementation related causes. Such scenarios may bereduced by better UE and/or eNB implementations. In such a scenario, aneNB may start decoding the secondary PUCCH signals for the UE insubframe n+k and may not receive CSI until the UE is able to detectPUCCH SCell and is ready for CSI transmission. Depending on how long theCSI transmission delay is, an eNB may perform some actions to remedy thesituation. In an example embodiment, the eNB may deactivate the PUCCHSCell when it does not receive the CSI after certain period.

In an example embodiment, a wireless device (UE) may receive at leastone message comprising configuration parameters of one or more secondarycells in a plurality of cells. The plurality of cells are grouped into aplurality of physical uplink control channel (PUCCH) groups. PUCCHgroups comprise a primary PUCCH group and a secondary PUCCH group. Thesecondary PUCCH group comprises a PUCCH secondary cell in the one ormore secondary cells. The wireless device receives anactivation/deactivation media-access-control control element (MAC CE) insubframe n. The activation/deactivation MAC CE indicates activation ofthe PUCCH secondary cell. In an example embodiment, the wireless devicemay start or restart a deactivation timer associated with the PUCCHsecondary cell in subframe n+8. The wireless device may starttransmitting channel state information (CSI) fields on the PUCCHsecondary cell in subframe n+8+k. The parameter k may be an integernumber depending, at least in part, on when a detection attempt, by thewireless device, for the PUCCH secondary cell is successful. Theparameter k may also depend, at least in part, on when a measured CSIfor the PUCCH secondary cell is available.

In an example embodiment of the invention, the wireless device mayreceive an activation/deactivation media-access-control control element(MAC CE) in subframe m. The activation/deactivation MAC CE may indicateactivation of a secondary cell in the primary PUCCH group. The wirelessdevice may start or restart a deactivation timer associated with thesecondary cell in subframe m+8. The UE may start transmitting channelstate information (CSI) fields on the PUCCH secondary cell in subframem+8. The wireless device may initially transmit a fixed CSI (for exampleinvalid and/or out of range) and then transmit the measured CSI for thesecondary cell when it is available. If valid CSI is available insubframe m+8, the UE may start transmission of the valid CSI at subframem+8. The wireless device may start transmission of CSI for SCell(s) inthe primary PUCCH group at subframe m+8, when the MAC activation commandfor the SCell is received in subframe m. On the other hand, the wirelessdevice may start transmission of CSI for the PUCCH SCell in subframem+8+k as described in example embodiments of the specifications.

In an example embodiment of the invention, the wireless device mayreceive an activation/deactivation media-access-control control element(MAC CE) in subframe p. The activation/deactivation MAC CE may indicateactivation of a first secondary cell in the secondary PUCCH cell group.The first secondary cell is different from the PUCCH SCell. The wirelessdevice may start or restart a deactivation timer associated with thesecondary cell in subframe p+8. The UE may start transmitting channelstate information (CSI) fields on the PUCCH secondary cell in subframep+8, if the PUCCH SCell is activated and ready for PUCCH uplinktransmissions. The UE may start transmitting channel state information(CSI) fields on the PUCCH secondary cell in subframe p+8+k, if the PUCCHSCell is activated and but not yet ready for PUCCH uplink transmissions.In an example embodiment, a MAC CE, received in a subframe, may indicateactivation a plurality of SCells including the PUCCH SCell, at least onesecondary cell in the secondary PUCCH group and/or at least onesecondary cell in the primary cell group.

In an example embodiment, an eNB may transmit an activation command toactivate an SCell in a UE with release 10 to 12 secondary cellconfiguration. The eNB may receive CSI for the secondary cell startingsubframe a+8, when the eNB transmitted an activation command in subframea. In an example embodiment, an eNB may transmit an activation commandto activate an SCell in a UE with release 13 or beyond, wherein thesecondary cell is in a primary PUCCH cell group. The eNB may receive CSIfor the secondary cell starting subframe b+8, when the eNB transmittedan activation command in subframe b. In an example embodiment, an eNBmay transmit an activation command to activate an SCell in a UE withrelease 13 or beyond, wherein the secondary cell is a PUCCH SCell. TheeNB may receive CSI for the PUCCH SCell starting subframe c+8+k, whenthe eNB transmitted an activation command in subframe c. The eNB maystart decoding CSI fields in the corresponding PUCCH resources dependingon the RRC configuration for the SCells in a UE.

In an example embodiment, when a PUCCH SCell is deactivated, the UE maynot immediately stop PUCCH transmissions. The PUCCH resources of anactivated PUCCH SCell is employed for uplink transmission of CSI ofPUCCH SCell and other activated SCell(s) in the secondary PUCCH group.The PUCCH resources of the activated PUCCH SCell is also employed foruplink transmission of ACK/NACK for downlink packets received on thePUCCH SCell and any other activated SCell(s) in the secondary PUCCHgroup. In the example embodiments of the invention if a UE receives adeactivation MAC command for a PUCCH SCell in subframe n or deactivationconditions are met in subframe n (e.g. deactivation timer expires), UEmay perform many of the following deactivation mechanisms in any one ofthe subframes from subframe n+1 to subframe n+8. The deactivationmechanisms performed in any one of the subframes from subframe n+1 tosubframe n+8 may include not transmitting SRS on the PUCCH SCell; nottransmitting on UL-SCH on the PUCCH SCell; not transmitting on RACH onthe PUCCH SCell; not monitoring the PDCCH on the PUCCH SCell; and/or notmonitoring the PDCCH for the PUCCH SCell.

In the example embodiments of the invention some of the deactivationmechanisms may be performed only in subframe n+8. The UE may stoptransmitting CSI on PUCCH on the PUCCH SCell in subframe n+8. Thisimplies that the UE does not stop reporting CSI for activated SCell(s)in the PUCCH SCell before subframe n+8. The UE stops reporting CSI foractivated SCell(s) in the PUCCH SCell on subframe n+8. The UE may stoptransmission of CSI for the PUCCH SCell on subframe n+8. In an exampleembodiment, if there is another activated SCell in the PUCCH group, theUE may stop transmission of CSI for the another activated SCell insubframe n+8.

The example embodiments of the invention may simplify the decodingprocess in the eNB receiving the PUCCH signals on the PUCCH SCell. Whenthe PUCCH SCell is deactivated in a given UE, the same PUCCH SCell mayremain in activated state in other UEs. Other UEs may continuouslytransmit signals on PUCCH resources of the PUCCH SCell, while the givenUE needs to stop PUCCH signal transmissions due to deactivation. If theeNB does not know when the given UE stops PUCCH signal transmissions,then eNB has to guess when the UE stops such transmissions. This maycomplicate the decoding process in an eNB. Many UEs may share the samePUCCH OFDM resource blocks. In the example embodiments of the invention,both the given UE and the eNB know that PUCCH signal CSI transmissionhas to stop exactly in subframe n+8. UE stops CSI transmission for allactivated SCell(s) in the secondary PUCCH group on PUCCH resources ofthe deactivated PUCCH SCell exactly in subframe n+8. The eNB also knowsthat it has to stop decoding for PUCCH signals transmitted by the UE onthe PUCCH resources of the PUCCH SCell in subframe n+8. Otherdeactivation mechanisms such as not transmitting SRS on the PUCCH SCell;not transmitting on UL-SCH on the PUCCH SCell; not transmitting on RACHon the PUCCH SCell; not monitoring the PDCCH on the PUCCH SCell; and/ornot monitoring the PDCCH for the S PUCCH Cell may be stopped in any oneof the subframes from subframe n+1 to subframe n+8. The exact timing ofthese stopping mechanisms are not required by eNB, since these stoppingmechanisms do not require complex decoding processes in the eNB.

FIG. 18 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 1810. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay comprise a primary cell and/or a PUCCH secondary cell. The primarycell may comprise a primary physical uplink control channel (PUCCH)transmitted to a base station. The PUCCH secondary cell may comprise asecondary PUCCH transmitted to the base station. According to anembodiment, the plurality of cells may be grouped into a plurality ofPUCCH groups comprising: a primary PUCCH group and a secondary PUCCHgroup. The primary PUCCH group may comprise the primary cell. Thesecondary PUCCH group may comprise the PUCCH secondary cell.

At 1820, the wireless device may receive, in subframe n, amedia-access-control control element indicating activation of the PUCCHsecondary cell.

At 1830, the wireless device may start transmission of channel stateinformation (CSI) fields for the PUCCH secondary cell from, for example,subframe n+8+k, where k may be an integer (0, 1, 2, 3, etc.) depending,at least in part, on when the PUCCH secondary cell is successfullydetected by the wireless device. According to an embodiment, thewireless device may start transmission of the CSI fields of an activatedcell in the secondary PUCCH group from subframe n+8+k.

According to an embodiment, the wireless device may start a deactivationtimer associated with the PUCCH secondary cell in subframe n+8.According to an embodiment, the wireless device may employ a nextavailable uplink resource for transmitting the CSI fields if there areno uplink resources for transmission of the CSI fields in subframen+8+k. According to an embodiment, a CSI field comprising an out ofrange CQI may be transmitted when no valid CSI field with a channelquality index (CQI) different from zero is available.

According to an embodiment, the PUCCH secondary cell may remaindetectable during a cell activation delay. According to an embodiment,the PUCCH secondary cell may be detected on a first attempt.

FIG. 19 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 1910. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may comprisea primary cell and/or a PUCCH secondary cell. The primary cell maycomprise a primary physical uplink control channel (PUCCH) received bythe base station. The PUCCH secondary cell may comprise a secondaryPUCCH received by the base station. At 1920, the base station maytransmit, in subframe n, a media-access-control control elementindicating activation of the PUCCH secondary cell in the wirelessdevice. At 1930, the base station may start reception of channel stateinformation (CSI) fields for the PUCCH secondary cell from the wirelessdevice from, for example, subframe n+8+k, where k may be an integerdepending, at least in part, on when the PUCCH secondary cell issuccessfully detected by the wireless device.

FIG. 20 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 2010. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay be grouped into a plurality of physical uplink control channel(PUCCH) groups. The PUCCH groups may comprise a primary PUCCH group anda secondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH. The secondary PUCCH group may comprise aPUCCH secondary cell with a secondary PUCCH.

At 2020, the wireless device may receive, in subframe m, a firstmedia-access-control control element (MAC CE) indicating activation of asecondary cell in the primary PUCCH group. At 2030, the wireless devicemay start transmission of channel state information (CSI) fields of thesecondary cell from, for example, subframe m+8. At 2040, the wirelessdevice may receive, in subframe n, a second MAC CE indicating activationof the PUCCH secondary cell. At 2050, the wireless device may starttransmission of CSI fields for the PUCCH secondary cell from subframen+8+k, where k may be an integer depending, at least in part, on whenthe PUCCH secondary cell is successfully detected by the wirelessdevice.

According to an embodiment, the wireless device may start transmissionof CSI fields of a first secondary cell in the secondary PUCCH groupfrom subframe n+8+k, where the second MAC CE further indicatesactivation of the first secondary cell. According to an embodiment, thewireless device may employ a next available uplink resource fortransmitting the CSI fields if there are no uplink resources fortransmitting a CSI field of the CSI fields for the PUCCH secondary cellin subframe n+8+k. According to an embodiment, the wireless device maystart transmission of CSI fields of an activated cell in the secondaryPUCCH group from subframe n+8+k. According to an embodiment, thewireless device may transmit a CSI field comprising an out of range CQIwhen no valid CSI field with a channel quality index (CQI) differentfrom zero is available.

According to an embodiment, the wireless device may start a firstdeactivation timer associated with the secondary cell in subframe m+8.The wireless device may also start a second deactivation timerassociated with the PUCCH secondary cell in subframe n+8. According toan embodiment, the PUCCH secondary cell may remain detectable during acell activation delay. According to an embodiment, the PUCCH secondarycell may be detected on a first attempt.

FIG. 21 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 2110. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may begrouped into a plurality of physical uplink control channel (PUCCH)groups. The PUCCH groups may comprise a primary PUCCH group and/or asecondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH. The secondary PUCCH group may comprise aPUCCH secondary cell with a secondary PUCCH.

At 2120, the base station may transmit, in subframe m, a firstmedia-access-control control element (MAC CE) indicating activation of asecondary cell in the primary PUCCH group in the wireless device. At2130, the base station may start reception of channel state information(CSI) fields of the secondary cell from subframe m+8. At 2140, the basestation may transmit, in subframe n, a second MAC CE indicatingactivation of the PUCCH secondary cell group in the wireless device. At2140, the base station may start reception of CSI fields for the PUCCHsecondary cell from, for example, subframe n+8+k from the wirelessdevice, where k is an integer depending, at least in part, on when thePUCCH secondary cell is successfully detected by the wireless device.

FIG. 22 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 2210. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay be grouped into a plurality of physical uplink control channel(PUCCH) groups. The PUCCH groups may comprise a primary PUCCH group anda secondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH. The secondary PUCCH group may comprise aPUCCH secondary cell with a secondary PUCCH.

At 2220, the wireless device may receive, in subframe m, a firstmedia-access-control control element (MAC CE) indicating activation of aplurality of secondary cells comprising: a secondary cell in the primaryPUCCH group, and the PUCCH secondary cell. At 2230, the wireless devicemay start transmission of channel state information (CSI) fields of thesecondary cell from subframe m+8. At 2240, the wireless device may starttransmission of CSI fields for the PUCCH secondary cell from subframem+8+k, where k may be an integer number depending, at least in part, onwhen the PUCCH secondary cell is successfully detected by the wirelessdevice. According to an embodiment, the wireless device may transmit aCSI field comprising an out of range CQI when no valid CSI field with achannel quality index (CQI) different from zero is available. Accordingto an embodiment, the wireless device may start transmission of CSIfields of a first secondary cell in the secondary PUCCH group fromsubframe m+8+k, where the first MAC CE further indicates activation ofthe first secondary cell.

According to an embodiment, the wireless device may start a firstdeactivation timer associated with the secondary cell in subframe m+8.The wireless device may also start a second deactivation timerassociated with the PUCCH secondary cell in subframe m+8.

FIG. 23 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 2310. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may begrouped into a plurality of physical uplink control channel (PUCCH)groups. The PUCCH groups may comprise a primary PUCCH group and/or asecondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH. The secondary PUCCH group may comprise aPUCCH secondary cell with a secondary PUCCH.

At 2320, the base station may transmit, in subframe m, a firstmedia-access-control control element (MAC CE) indicating activation of aplurality of secondary cells in the wireless device. The plurality ofcells may comprise: a secondary cell in the primary PUCCH group, and thePUCCH secondary cell. At 2330, the base station may start reception ofchannel state information (CSI) fields of the secondary cell from, forexample, subframe m+8. At 2330, the base station may start reception ofCSI fields for the PUCCH secondary cell from, for example, subframem+8+k from the wireless device, where k may be an integer numberdepending, at least in part, on when the PUCCH secondary cell issuccessfully detected by the wireless device.

FIG. 24 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 2410. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay be grouped into a plurality of physical uplink control channel(PUCCH) groups. The PUCCH groups may comprise a primary PUCCH group anda secondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH transmitted to the base station. The secondaryPUCCH group may comprise a PUCCH secondary cell with a secondary PUCCHtransmitted to the base station. According to an embodiment, theconfiguration parameters may comprise a plurality of common parameters.Additionally, the configuration parameters may comprise a plurality ofdedicated parameters comprising a deactivation timer value.

At 2420, the wireless device may receive, in subframe n, amedia-access-control control element indicating activation of asecondary cell in the secondary PUCCH group. According to an embodiment,the media-access-control control element may comprise a bitmap.

At 2430, the wireless device may start transmission of channel stateinformation (CSI) fields for the secondary cell from, for example,subframe n+8+k. If the activation of the PUCCH secondary cell iscompleted before subframe n+8, k may be equal to zero. If the activationof the PUCCH secondary cell is completed on or after subframe n+8, k maybe greater than 0 and may depend on when the activation of the PUCCHsecondary cell is completed. According to an embodiment, a deactivationtimer associated with the secondary cell in subframe n+8 may be started.According to an embodiment, the wireless device may employ a nextavailable uplink resource for reporting a CSI field of the CSI fields insubframe n+8+k if there are no uplink resources for reporting the CSIfield of the CSI fields in subframe n+8+k. According to an embodiment,transmission of CSI fields of an activated cell in the secondary PUCCHgroup from subframe n+8+k may be started. According to an embodiment, aCSI field comprising an out of range CQI may be transmitted when novalid CSI field with a channel quality index different from zero isavailable.

FIG. 25 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 2510. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may begrouped into a plurality of physical uplink control channel (PUCCH)groups. The PUCCH groups may comprise a primary PUCCH group and asecondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH received by the base station. The secondaryPUCCH group may comprise a PUCCH secondary cell with a secondary PUCCHreceived by the base station. According to an embodiment, theconfiguration parameters may comprise a plurality of common parameters.Additionally, the configuration parameters may comprise a plurality ofdedicated parameters comprising a deactivation timer value.

At 2520, the base station may transmit, in subframe n, amedia-access-control control element indicating activation of asecondary cell in the secondary PUCCH group. According to an embodiment,the media-access-control control element may comprise a bitmap.

At 2530, the base station may start reception of channel stateinformation (CSI) fields for the secondary cell from, for example,subframe n+8+k. If the activation of the PUCCH secondary cell iscompleted before subframe n+8, k may be equal to zero. If the activationof the PUCCH secondary cell is completed on or after subframe n+8, k maybe greater than 0 and may depend on when the activation of the PUCCHsecondary cell is completed. According to an embodiment, a deactivationtimer associated with the secondary cell in subframe n+8 may be started.According to an embodiment, the wireless device may employ a nextavailable uplink resource for reporting a CSI field of the CSI fields insubframe n+8+k if there are no uplink resources for reporting the CSIfield of the CSI fields in subframe n+8+k. According to an embodiment,transmission of CSI fields of an activated cell in the secondary PUCCHgroup from subframe n+8+k may be started. According to an embodiment, aCSI field comprising an out of range CQI may be transmitted when novalid CSI field with a channel quality index different from zero isavailable.

FIG. 26 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 2610. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay be grouped into a plurality of physical uplink control channel(PUCCH) groups. The PUCCH groups may comprise a primary PUCCH group anda secondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH. The secondary PUCCH group may comprise aPUCCH secondary cell (SCell) with a secondary PUCCH. According to anembodiment, the configuration parameters may comprise a plurality ofcommon parameters. According to an embodiment, the configurationparameters may comprise a plurality of common parameters. Additionally,the configuration parameters may comprise a plurality of dedicatedparameters comprising a deactivation timer value.

At 2620, the wireless device may receive, in subframe n, amedia-access-control control element indicating activation of aplurality of SCells. The plurality of SCells may comprise: a first SCellin the primary PUCCH group, and a second SCell in the secondary PUCCHgroup. According to an embodiment, the media-access-control controlelement may comprise a bitmap.

At 2630, the wireless device may start transmission of channel stateinformation (CSI) fields for the first SCell from, for example, subframen+8. At 2640, the wireless device may start transmission of CSI fieldsfor the second SCell from, for example, subframe n+8+k. If theactivation of the PUCCH SCell is completed before subframe n+8, may beequal to zero. If the activation of the PUCCH SCell is completed on orafter subframe n+8, k may be greater than 0 and depend on when theactivation of the PUCCH SCell is completed. According to an embodiment,a first deactivation timer associated with the first SCell in subframen+8 may start. A second deactivation timer associated with the secondSCell in subframe n+8 may also be started. According to an embodiment,the wireless device may employ a next available uplink resource forreporting a CSI field of the CSI fields for the second SCell in subframen+8+k if there are no uplink resources for reporting the CSI field.According to an embodiment, transmission of CSI fields of an activatedcell in the secondary PUCCH group from subframe n+8+k may start.According to an embodiment, a CSI field comprising an out of range CQImay be transmitted when no valid CSI field with a channel quality indexdifferent from zero is available.

FIG. 27 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 2510. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may begrouped into a plurality of physical uplink control channel (PUCCH)groups. The PUCCH groups may comprise a primary PUCCH group and asecondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH. The secondary PUCCH group may comprise aPUCCH secondary cell with a secondary PUCCH. According to an embodiment,the configuration parameters may comprise a plurality of commonparameters, and/or a plurality of dedicated parameters comprising adeactivation timer value.

At 2720, a media-access-control control element indicating activation ofa plurality of SCells may be transmitted in subframe n. The plurality ofSCells may comprise: a first SCell in the primary PUCCH group, and asecond SCell in the second PUCCH group. According to an embodiment, themedia-access-control control element may comprise a bitmap.

At 2730, reception may be started, from the wireless device, of channelstate information (CSI) fields for the first SCell from subframe n+8. At2740, reception may be started, from the wireless device, of CSI fieldsfor the second SCell from subframe n+8+k. If the activation of the PUCCHSCell is completed before subframe n+8, k may be equal to zero. If theactivation of the PUCCH SCell is completed on or after subframe n+8, kmay be greater than 0 and may depend on when the activation of the PUCCHSCell is completed. According to an embodiment, a first deactivationtimer associated with the first SCell in subframe n+8 may be started.Additionally, a second deactivation timer associated with the secondSCell in subframe n+8 may be started. According to an embodiment, thebase station may receive the CSI field of the CSI fields for the secondSCell in subframe n+8+k in a next available uplink resource forreceiving CSI fields from the wireless device if there are no uplinkresources for receiving, from the wireless device, the a CSI field ofthe CSI fields for the second SCell in subframe n+8+k. According to anembodiment, a CSI field comprising an out of range CQI may be receivedwhen no valid CSI field with a channel quality index different from zerois available.

In this specification, the activation of the PUCCH secondary cell may beconsidered completed in subframe i, when the PUCCH secondary cellbecomes capable of transmitting CSI in subframe i+1. When the PUCCHsecondary cell is capable of transmitting CSI in subframe i+1 and startstransmitting CSI from subframe i+1, it may be implied that the UEtransmits CSI in the first available CSI resources on PUCCH SCell on orafter subframe i+1.

FIG. 28 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 2810. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay be grouped into a plurality of physical uplink control channel(PUCCH) groups. The PUCCH groups may comprise a primary PUCCH group anda secondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH transmitted to the base station. The secondaryPUCCH group may comprise a PUCCH secondary cell with a secondary PUCCHtransmitted to the base station. According to an embodiment, at leastone message may comprise a plurality of dedicated parameters comprisinga deactivation timer parameter.

At 2820, the wireless device may receive, in subframe n, a media accesscontrol (MAC) command indicating deactivation of the PUCCH secondarycell. According to an embodiment, the MAC command may comprise a bitmap.According to an embodiment, the MAC command may further indicate adeactivation of a first secondary cell.

At 2830, the wireless device may stop transmission of channel stateinformation for a first secondary cell in the secondary PUCCH group in,for example, subframe n+8. The first secondary cell may be differentfrom the PUCCH secondary cell. According to an embodiment, the wirelessdevice may stop a deactivation timer associated with the first secondarycell on or before subframe n+8. According to an embodiment, the wirelessdevice may stop a monitoring of a downlink control channel of the firstsecondary cell on or before subframe n+8. According to an embodiment,the wireless device may stop uplink transmission on the first secondarycell before stopping uplink transmission on the PUCCH secondary cell.

FIG. 29 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 2910. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may begrouped into a plurality of physical uplink control channel (PUCCH)groups. The PUCCH groups may comprise a primary PUCCH group and asecondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH transmitted to the base station. The secondaryPUCCH group may comprise a PUCCH secondary cell with a secondary PUCCHtransmitted to the base station. At 2920, the bases station maytransmit, in subframe n, a media access control (MAC) command indicatingdeactivation of the PUCCH secondary cell in the wireless device. At2930, the bases station may stop reception of channel state informationfor a first secondary cell in the secondary PUCCH group from thewireless device in, for example, subframe n+8. The first secondary cellmay be different from the PUCCH secondary cell.

FIG. 30 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A wireless device may receive at least onemessage from a base station at 3010. The message may compriseconfiguration parameters of a plurality of cells. The plurality of cellsmay be grouped into a plurality of physical uplink control channel(PUCCH) groups. The PUCCH groups may comprise a primary PUCCH group anda secondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH transmitted to the base station. The secondaryPUCCH group may comprise a PUCCH secondary cell with a secondary PUCCHtransmitted to the base station. According to an embodiment, at leastone message may comprise a plurality of dedicated parameters comprisinga deactivation timer parameter.

At 3020, the wireless device may receive, in subframe n, a media accesscontrol (MAC) command indicating deactivation of a first secondary celland the PUCCH secondary cell. According to an embodiment, the MACcommand comprises a bitmap.

At 3030, the wireless device may stop uplink transmission on the PUCCHsecondary cell on subframe n+8. At 3040, the wireless device may stopuplink transmission on the first secondary cell before subframe n+8.According to an embodiment, the wireless device may stop a deactivationtimer associated with the first secondary cell on or before subframen+8. According to an embodiment, the wireless device may stop amonitoring of a downlink control channel of the first secondary cell onor before subframe n+8. According to an embodiment, a deactivation timerof the PUCCH secondary cell may be disabled.

FIG. 31 is an example flow diagram as per an aspect of an embodiment ofthe present invention. A base station may transmit at least one messageto a wireless device at 3110. The message may comprise configurationparameters of a plurality of cells. The plurality of cells may begrouped into a plurality of physical uplink control channel (PUCCH)groups. The PUCCH groups may comprise a primary PUCCH group and asecondary PUCCH group. The primary PUCCH group may comprise a primarycell with a primary PUCCH transmitted to the base station. The secondaryPUCCH group may comprise a PUCCH secondary cell with a secondary PUCCHtransmitted to the base station. At 3120, the bases station maytransmit, in subframe n, a media access control (MAC) command indicatingdeactivation of the PUCCH secondary cell in the wireless device. At3130, the bases station may stop reception of channel state informationfor a first secondary cell in the secondary PUCCH group from thewireless device in, for example, subframe n+8. The first secondary cellmay be different from the PUCCH secondary cell. At 3120, the basesstation may transmit, in subframe n, a media access control (MAC)command indicating deactivation of a first secondary cell and/or thePUCCH secondary cell in the wireless device. At 3130, the bases stationmay stop uplink reception on the PUCCH secondary cell on subframe n+8from the wireless device. At 3140, the bases station may stop uplinkreception on the first secondary cell before subframe n+8 from thewireless device.

A primary PUCCH group may comprise a group of serving cells including aPCell whose PUCCH signaling may be associated with the PUCCH on thePCell. A PUCCH group may comprise either a primary PUCCH group and/or asecondary PUCCH group. A PUCCH SCell may comprise a Secondary Cellconfigured with a PUCCH. A secondary PUCCH group may comprise a group ofSCells whose PUCCH signaling is associated with the PUCCH on the PUCCHSCell. A Timing Advance Group may comprise a group of serving cellsconfigured by and RRC and that, for the cells with an UL configured, usethe same timing reference cell and/or the same Timing Advance value. APrimary Timing Advance Group may comprise a Timing Advance Groupcontaining the PCell. A Secondary Timing Advance Group may comprise aTiming Advance Group not containing the PCell. A PUCCH may betransmitted on a PCell, a PUCCH SCell (if such is configured in CA)and/or on a PSCell (in DC).

With regard to carrier aggregation, the configured set of serving cellsfor a UE may consist of one PCell and one or more SCell. If DC is notconfigured, one additional PUCCH may be configured on an SCell, thePUCCH SCell. When a PUCCH SCell is configured, RRC may configure themapping of each serving cell to a primary PUCCH group or a secondaryPUCCH group (e.g., for each SCell whether the PCell and/or the PUCCHSCell is employed for the transmission of ACK/NAKs and CSI reports).

An example of an Activation/Deactivation Mechanism comprises an E-UTRANensuring that while a PUCCH SCell is deactivated, SCells of a secondaryPUCCH group may not be activated. With the exception of PUCCH SCell, onedeactivation timer may be maintained per SCell, but one common value maybe configured per CG by an RRC.

In an example embodiment, with regard to SCell Activation DelayRequirement(s) for a Deactivated SCell, requirements may apply for a UEconfigured with one downlink SCell. May be applicable for E-UTRA FDD,E-UTRA TDD and/or E-UTRA TDD-FDD carrier aggregation. The delay withinwhich the UE may be able to activate the deactivated SCell may dependsupon specified conditions. Upon receiving an SCell activation command insubframe n, the UE may be capable to transmit a valid CSI report andapply actions related to an activation command for the SCell beingactivated no later than in subframe n+24, provided the followingconditions may be met for the SCell: during the period equal to max(5measCycleSCell, 5 DRX cycles) before the reception of the SCellactivation command, the UE has sent a valid measurement report for theSCell being activated and/or the SCell being activated remainsdetectable according to cell identification conditions; and/or an SCellbeing activated also remains detectable during the SCell activationdelay according to cell identification conditions. Otherwise, uponreceiving the SCell activation command in subframe n, the UE may becapable to transmit a valid CSI report and apply actions related to theactivation command for the SCell being activated no later than insubframe n+34, provided the SCell may be successfully detected on afirst attempt.

With regard to an SCell activation delay requirement for a deactivatedPUCCH SCell, requirements may apply for a UE configured with onedownlink SCell and when a PUCCH is configured for the SCell beingactivated. If the UE has a valid TA for transmitting on an SCell, thenthe UE may be able to transmit a valid CSI report and apply actionsrelated to the SCell activation command for the SCell being activated onthe PUCCH SCell no later than in subframe n+Tactivate_basic, where: a TAis considered to be valid provided that a TimeAlignmentTimer associatedwith the TAG containing the PUCCH SCell is running; and/orTactivate_basic is the SCell activation delay.

In this specification, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” In this specification,the term “may” is to be interpreted as “may, for example.” In otherwords, the term “may” is indicative that the phrase following the term“may” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, MATLAB or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using FDD communication systems. However, one skilled in the art willrecognize that embodiments of the invention may also be implemented in asystem comprising one or more TDD cells (e.g. frame structure 2 and/orframe structure 3-licensed assisted access). The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. Only a limited number of example combinations areshown to indicate to one skilled in the art the possibility of featuresthat may be combined in various embodiments to create enhancedtransmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112, paragraph 6. Claims that do not expressly include the phrase“means for” or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive aconfiguration of a physical uplink control channel (PUCCH) groupcomprising: a first secondary cell with a secondary PUCCH; and a secondsecondary cell; receive, in a first subframe, a media access control(MAC) command comprising a bitmap indicating deactivation of the firstsecondary cell; and stop, in response to the deactivation of the firstsecondary cell, transmission of channel state information for the secondsecondary cell in a second subframe that is eight subframes after thefirst subframe, wherein the stopping does not occur before the secondsubframe.
 2. The wireless device of claim 1, wherein to receive theconfiguration, the instructions, when executed by the one or moreprocessors, further cause the wireless device to receive configurationsof PUCCH groups comprising: a primary PUCCH group comprising a primarycell with a primary PUCCH; and a secondary PUCCH group comprising thePUCCH group.
 3. The wireless device of claim 1, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to stop a monitoring of a downlink control channelof the second secondary cell on or before the second subframe that iseight subframes after the first subframe.
 4. The wireless device ofclaim 1, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to stop a deactivationtimer associated with the second secondary cell on or before the secondsubframe that is eight subframes after the first subframe.
 5. Thewireless device of claim 1, wherein the configuration comprisesdedicated parameters comprising a deactivation timer parameter.
 6. Thewireless device of claim 1, wherein the bitmap, in the MAC command,further indicates a deactivation of the second secondary cell.
 7. Thewireless device of claim 1, wherein the instructions, when executed bythe one or more processors, further cause the wireless device to stopuplink transmission on the second secondary cell before stopping uplinktransmission on the first secondary cell.
 8. A method comprising:transmitting, by a base station to a wireless device, a configuration ofa physical uplink control channel (PUCCH) group comprising: a firstsecondary cell with a secondary PUCCH; and a second secondary cell;transmitting, in a first subframe, a media access control (MAC) commandcomprising a bitmap indicating deactivation of the first secondary cell;and stopping, in response to the deactivation of the first secondarycell, reception of channel state information for the second secondarycell in a second subframe that is eight subframes after the firstsubframe, wherein the stopping does not occur before the secondsubframe.
 9. The method of claim 8, wherein the transmitting theconfiguration comprises transmitting configurations of PUCCH groupscomprising: a primary PUCCH group comprising a primary cell with aprimary PUCCH; and a secondary PUCCH group comprising the PUCCH group.10. The method of claim 8, further comprising stopping transmission of adownlink control channel of the second secondary cell on or before thesecond subframe that is eight subframes after the first subframe. 11.The method of claim 8, further comprising stopping, for the wirelessdevice, a deactivation timer associated with the second secondary cellon or before the second subframe that is eight subframes after the firstsubframe.
 12. The method of claim 8, wherein the configuration comprisesdedicated parameters comprising a deactivation timer parameter.
 13. Themethod of claim 8, wherein the bitmap, in the MAC command, furtherindicates a deactivation of the second secondary cell.
 14. The method ofclaim 8, further comprising stopping uplink reception, from the wirelessdevice, on the second secondary cell before stopping uplink reception,from the wireless device, on the first secondary cell.
 15. A basestation comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe base station to: transmit, to a wireless device, a configuration ofa physical uplink control channel (PUCCH) group comprising: a firstsecondary cell with a secondary PUCCH; and a second secondary cell;transmit, in a first subframe, a media access control (MAC) commandcomprising a bitmap indicating deactivation of the first secondary cell;and stop, in response to the deactivation of the first secondary cell,reception of channel state information for the second secondary cell ina second subframe that is eight subframes after the first subframe,wherein the stopping does not occur before the second subframe.
 16. Thebase station of claim 15, wherein to transmit the configuration, theinstructions, when executed by the one or more processors, further causethe base station to transmit configurations of PUCCH groups comprising:a primary PUCCH group comprising a primary cell with a primary PUCCH;and a secondary PUCCH group comprising the PUCCH group.
 17. The basestation of claim 15, wherein the instructions, when executed by the oneor more processors, further cause the base station to stop transmissionof a downlink control channel of the second secondary cell on or beforethe second subframe that is eight subframes after the first subframe.18. The base station of claim 15, wherein the instructions, whenexecuted by the one or more processors, further cause the base stationto stop, for the wireless device, a deactivation timer associated withthe second secondary cell on or before the second subframe that is eightsubframes after the first subframe.
 19. The base station of claim 15,wherein the configuration comprises dedicated parameters comprising adeactivation timer parameter.
 20. The base station of claim 15, whereinthe bitmap, in the MAC command, further indicates a deactivation of thesecond secondary cell.